home *** CD-ROM | disk | FTP | other *** search
- Path: aargh.incubus.sub.org!marc
- From: marc@aargh.incubus.sub.org (Marc 'Nepomuk' Heuler)
- Newsgroups: comp.sys.amiga.programmer,comp.sys.amiga.applications
- Subject: How to break an ARexx program?
- Message-ID: <F9DVx*cia@aargh.incubus.sub.org>
- Date: Tue, 09 Jan 1996 18:18:17 CET
- Reply-To: marc@aargh.incubus.sub.org
- FollowUp-To: comp.sys.amiga.programmer
- Organization: Data Design
- X-Newsreader: Arn V1.03a
-
- I need to break an ARexx program on a very special setup.
-
- The ways I know to break an ARexx program are the following - and all of
- them can't be used for some reason:
-
- 1. Hit ^C. Not possible because nobody is around to hit ^C.
-
- 2. Use InsertKey to hit ^C. Not possible because the computer is
- protected against unauthorized keyboard/mouse input with a password
- screen blanker. Unblanking from remote to InsertKey ^C would be a
- security disaster.
-
- 3. Use Break <procnum>. Does not work, I tried.
-
- 4. Use RexxC/HI. This works, but is global. It also breaks the logfile
- pipe daemon and thereby causes all programs to freeze on further
- logfile output.
-
- 5. Use the PRAGMA('ID') task block to set SIGBREAKF_CTRL_C signal. This
- does not work, I tried.
-
- 6. Continously check for a temporary file. If it's gone, exit. This does
- work. However, the ARexx program flow splits up in many parts, even
- loading subprograms from disk. The main loop can be omitted by the
- program flow for as long as 10 minutes.
-
- The program, however, must response quickly to a break
- (time limit = remote users' patience)
-
- 7. Add an ARexx port and read the break command from there. Does work, but
- is inappropriate - see reasoning 6.
-
- Now, is there anything I missed? I can't imagine that my setup related
- requirements are too strong for ARexx?!
-